Systems and methods for condition compliance

ABSTRACT

In some embodiments, apparatuses and methods are provided herein useful to monitoring condition compliance. In some embodiments, a system comprises a child device comprising a child device sensor configured to capture condition data, a child device memory configured to store the condition data, a child device transmitter configured to transmit the condition data, and a control circuit configured to cause transmission of a discovery message, receive acknowledgment messages, determine if the discovery message reached a parent device, if the discovery message reached a parent device, cause transmission of the condition data to the parent device, and if the discovery message did not reach a parent device, determine, from the other devices, one of the other devices, and cause transmission of the condition data to the one of the other devices, and the parent device configured to store and transmit condition data received from a plurality of child devices.

CROSS-REFERENCE TO RELATED APPLICATION

This application claims the benefit of U.S. Provisional Application No. 62/744,766, filed Oct. 12, 2018, which is incorporated by reference in its entirety herein.

TECHNICAL FIELD

This invention relates generally to the transport of goods and, more particularly, to monitoring condition compliance during the transport of goods.

BACKGROUND

Many products are in transit for a period of time before they arrive at a retail facility to be offered for sale. This period of time may be short (e.g., a number of hours) or long (e.g., a number of months). Additionally, products may sit a distribution center or in a stock room for a period of time before they are offered for sale. This period of time may be short or long. Dependent upon the type of the product, certain conditions must be maintained during transit and storage. For example, refrigerated items must be kept within specified temperature ranges to prevent spoilage. Maintaining the products, or the environment in which the products are transported/stored, with respect to a necessary or desired condition is generally referred to as condition compliance. Typically, condition compliance is monitored with a sensor located within a delivery vehicle or storage location. While such condition compliance is helpful in determining whether the appropriate conditions have been maintained, it may only indicate whether the condition was maintained near the sensor. This is problematic if the area in which the products are located is configured in such a way that conditions vary throughout the area. Consequently, better systems are needed to monitor condition compliance.

BRIEF DESCRIPTION OF THE DRAWINGS

Disclosed herein are embodiments of systems, apparatuses, and methods pertaining to monitoring condition compliance. This description includes drawings, wherein:

FIG. 1 depicts a delivery vehicle 100 transporting containers 102 to a distribution center 108, according to some embodiments;

FIG. 2 depicts a system 200 for monitoring condition compliance, according to some embodiments; and

FIG. 3 is a flow chart depicting example operations for monitoring condition compliance, according to some embodiments.

Elements in the figures are illustrated for simplicity and clarity and have not necessarily been drawn to scale. For example, the dimensions and/or relative positioning of some of the elements in the figures may be exaggerated relative to other elements to help to improve understanding of various embodiments of the present invention. Also, common but well-understood elements that are useful or necessary in a commercially feasible embodiment are often not depicted in order to facilitate a less obstructed view of these various embodiments of the present invention. Certain actions and/or steps may be described or depicted in a particular order of occurrence while those skilled in the art will understand that such specificity with respect to sequence is not actually required. The terms and expressions used herein have the ordinary technical meaning as is accorded to such terms and expressions by persons skilled in the technical field as set forth above except where different specific meanings have otherwise been set forth herein.

DETAILED DESCRIPTION

Generally speaking, pursuant to various embodiments, systems, apparatuses, and methods are provided herein useful to monitoring condition compliance. In some embodiments, a system for monitoring condition compliance comprises a child device, wherein the child device is configured to be incorporated with a container housing a product, the child device comprising a child device sensor, wherein the child device sensor is configured to capture condition data associated with the product, a child device memory, wherein the child device memory is configured to store the condition data associated with the product, a child device transmitter, wherein the child device transmitter is configured to transmit the condition data associated with the product, and a control circuit, wherein the control circuit is configured to cause transmission, via the child device transmitter, of a discovery message, receive, from other devices via the child device transmitter, acknowledgment messages, determine, based on the acknowledgment messages, if the discovery message reached a parent device, if the discovery message reached a parent device, cause transmission of the condition data associated with the product to the parent device, and if the discovery message did not reach a parent device, determine, from the other devices, one of the other devices that is furthest from the child device, and cause transmission of the condition data associated with the product to the one of the other devices furthest from the child device, and the parent device, the parent device configured to store condition data received from a plurality of child devices, and transmit, to a master device, the condition data received from the plurality of child devices.

As previously discussed, monitoring condition compliance is important to retailers. As one example, it is important that appropriate conditions are maintained when transporting perishables and storing perishables before sale. Not only is it costly when condition compliance is not maintained (e.g., if products are no longer fit for sale due to a lack of condition compliance and must be discarded), but it can also be unsafe for customers (e.g., if a customer consumes a product that is not safe for consumption due to a lack of condition compliance). Described herein, are systems, methods, and apparatuses to aid in monitoring condition compliance.

In one embodiment, the systems, methods, and apparatuses include three types of devices: 1) child devices, 2) parent devices, and 3) master devices. The child devices include sensors to capture condition data. The child devices can be deployed at a product level or for multiple products (e.g., a package, pallet, etc.). The child devices transmit the condition data to the parent devices. The parent devices are located in a cargo area of a delivery vehicle. When the delivery vehicle reaches its destination, or a location along the route to its destination, the parent devices transmit the condition data received from the child devices to a master device located at the destination, or the location on the route to the destination.

Because the child devices are located throughout the cargo area of the delivery vehicle, the child devices can better capture conditions across the cargo area of the delivery vehicle. Additionally, because the parent devices transmit the condition data to the master device, as opposed to the child devices transmitting the condition data directly to the master device, the master device is less likely to be overwhelmed by the transmissions. The discussion of FIG. 1 provides background regarding such a system.

FIG. 1 depicts a delivery vehicle 100 transporting containers 102 to a distribution center 108, according to some embodiments. The delivery vehicle 100 includes a cargo area 112. Although the delivery vehicle 100 depicted in FIG. 1 is of the truck and trailer variety, embodiments are not so limited. For example, the delivery vehicle 100 can be any suitable type of terrestrial vehicle (e.g., car, train, etc.), nautical vehicle (e.g., a boat, ship, etc.), or an aerial vehicle (e.g., a helicopter, plane, etc.). Additionally, the cargo area 112 need not be distinct from the rest of the delivery vehicle 100. For example, the cargo area 112 of a van-type delivery vehicle may not be separated from other areas of the van.

The containers 102 are located in the cargo area 112. The containers 102 can house a single product (e.g., the containers 102 can be packaging for a product) or multiple products (e.g., the containers 102 can be boxes or crates housing a number of products, pallets, etc.). Child devices 106 are incorporated with the containers 102. For example, if the containers 102 are boxes housing a number of products, the child devices 106 can be located within, under, near, etc. the boxes. If the containers 102 are product packaging, the child devices 106 can be located within, under, near, etc. the product packaging.

The child devices 106 include sensors (i.e., child device sensors). The sensors are configured to capture condition data associated with the container (i.e., one or more products housed in the containers 102). The sensors can be of any suitable type (e.g., temperature sensors (i.e., thermometers), humidity sensors, light sensors, orientation sensors (e.g., gyroscopes), moisture sensors, weight sensors, magnetic field sensors, electrical sensors, etc.) and can be a combination of multiple types of sensors. Accordingly, the sensors can capture any desired type of condition data (e.g., temperature, humidity, light exposure, orientation, the presence of moisture, weight data, magnetic field data, electrical data, etc.). The sensors can capture the condition data with any suitable frequency (e.g., continuously, every minute, every five minutes, every 30 minutes, every hour, every day, etc.). Additionally, in some embodiments, the frequency with which condition data is captured may be dependent upon the type of condition monitored.

The child devices 106 store the condition data captured by the sensors. In some embodiments, the child devices 106 can store condition data for the length of the journey. In other embodiments, the child devices 106 may only store, or be capable of storing, condition data for a portion of the journey. In either case, the child devices 106 may transmit the condition data at any suitable frequency. These intervals can be regular or random, and in some embodiments, dependent upon the condition being monitored or events encountered. For example, temperature data may be transmitted every five minutes, whereas orientation data may only be transmitted every hour or when potential movement is detected (e.g., based on accelerometer data).

The child devices 106 transmit the condition data to parent devices 104. The parent devices 104 are located on the delivery vehicle 100 (e.g., in a cab of the delivery vehicle 100, in the cargo areas 112 of the delivery vehicle 100, on top of the delivery vehicle 100, etc.). Although the delivery vehicle depicted in FIG. 1 includes four parent devices 104 located about the periphery of the cargo area 112, such is not required. That is, the delivery vehicle 100 can include greater, or fewer, than four parent devices 104. For example, the delivery vehicle 100 may include only one parent device 104 (e.g., located centrally, near a door, etc.) or several parent devices 104 (e.g., located at predetermined distances and locations about the delivery vehicle 100).

In the case that one of the child devices 106 cannot transmit the condition data to one of the parent devices 104 (e.g., none of the parents devices 104 are within transmission range of the one of the child devices 106), the one of the child devices 106 can transmit its condition data to another one of the child devices 106, as discussed in more detail with respect to FIGS. 2 and 3 . In such embodiments, other ones of the child devices 106 receiving the condition data from the one of the child devices 106 can relay the condition data to one of the parent devices 104, acting as a mesh network.

The parent devices 104 receive, and store, the condition data received from the child devices 106. When the delivery vehicle 100 arrives at a destination (e.g., a retail facility, a checkpoint, a distribution center 108, etc.), the parent devices 104 transmit the received condition data to master devices 110. The master devices 110 are located at the destination. In the example depicted in FIG. 1 , the delivery vehicle 100 is arriving at a distribution center 108. The distribution center 108 includes at least one master device 110. The master devices 110 can be located about the distribution center 108, for example, near doors or docks of the distribution center 108.

While the discussion of FIG. 1 provides background regarding monitoring condition compliance, the discussion of FIG. 2 provides additional detail regarding a system for monitoring condition compliance.

FIG. 2 depicts a system 200 for monitoring condition compliance, according to some embodiments. The system includes a child device 210 and a parent device 212. The child device 210 includes a child device sensor 204, a child device transmitter 206, a child device memory 208, and a control circuit 202.

The child device 210 is configured to be incorporated with a container housing a product, or multiple products. For example, the child device 210 can be placed in the container, on the container, near the container, etc. The child device sensor 204 is configured to capture condition data associated with the product(s) (i.e., a product housed by the container). The condition monitored by the child device sensor 204 can be any suitable type of condition. For example, the child device sensor 204 can capture temperature data, humidity data, light exposure data, orientation data (e.g., orientation of the product and/or the container), moisture data, weight data, magnetic field data, electrical data, etc. Accordingly, the child device sensor 204 can be of any suitable type, including multiple sensors.

In embodiments in which the child device sensor 204 is, or includes, a weight sensor, the child device sensor 204 can be used to detect the presence of products in or on the container. In such embodiments, the child device sensor can be used to control a state of the child device 210 (e.g., a power state, a wake state, etc.). For example, the child device 210 may turn on when the weight sensor detects that a product is present in the container and turn off when the product is removed and/or no products are detecting in the container. Similarly, other types of sensors can be used to achieve this result (e.g., motion sensors, proximity sensors, light sensors, etc.). Regardless of the type of sensors used to control the state of the child device 210, battery life and/or operational life of the child device 210 may be increased. Such control may be important in embodiments in which the child device 210 includes a power supply such as a battery. Additionally, in embodiments in which the child device 210 is powered remotely (e.g., via inductive means), turning the child device 210 off when a product is not present may limit the transmission overhead and/or decrease the amount of data stored at the child device 210, other child devices, or the parent device 212.

The child device memory 208 stores the condition data captured by the child device sensor 204. The child device memory can be of any suitable type (e.g., flash memory, a hard disk, etc.). The child device memory 208 can be capable of storing a relatively limited amount of condition data (e.g., the amount of data captured over 10 minutes, 30 minutes, one hour, one day, etc.) or an unlimited amount of condition data, relative to the size and quantity of the condition data (e.g., all condition data captured during a journey). In some embodiments, the frequency with which the condition data is transmitted is dependent upon the storage capabilities of the child device memory 208. For example, the transmission frequency can be based on a time period in which the child device memory 208 should not have reached capacity, or can occur when the capacity of the child device memory 208 is reached. Additionally, in some embodiments, as described in more detail with respect to FIG. 3 , the child device memory 208 can store condition data from other child devices.

The child device transmitter 206 is configured to transmit the condition data. In some embodiments, the child device transmitter 206 can receive data and/or messages from other devices, such as another child device, the parent device 212, a master device, a backend server, etc. In such embodiments, the child device transmitter 206 acts as a transceiver. Alternatively, the child device 210 can include distinct transmitters and receivers. In some embodiments, the child device transmitter 206 is configured to transmit via a different transmission medium than the parent device 212. For example, the child device transmitter 206 can transmit via a radio wave frequency (e.g., AM or FM bands) and the parent device 212 can transmit via the 802.11 standard and/or a radio wave frequency.

The control circuit 202 can comprise a fixed-purpose hard-wired hardware platform (including but not limited to an application-specific integrated circuit (ASIC) (which is an integrated circuit that is customized by design for a particular use, rather than intended for general-purpose use), a field-programmable gate array (FPGA), and the like) or can comprise a partially or wholly-programmable hardware platform (including but not limited to microcontrollers, microprocessors, and the like). These architectural options for such structures are well known and understood in the art and require no further description here. The control circuit 202 is configured (for example, by using corresponding programming as will be well understood by those skilled in the art) to carry out one or more of the steps, actions, and/or functions described herein.

By one optional approach the control circuit 202 operably couples to a memory. The memory may be integral to the control circuit 202 or can be physically discrete (in whole or in part) from the control circuit 202 as desired. This memory can also be local with respect to the control circuit 202 (where, for example, both share a common circuit board, chassis, power supply, and/or housing) or can be partially or wholly remote with respect to the control circuit 202 (where, for example, the memory is physically located in another facility, metropolitan area, or even country as compared to the control circuit 202).

This memory can serve, for example, to non-transitorily store the computer instructions that, when executed by the control circuit 202, cause the control circuit 202 to behave as described herein. As used herein, this reference to “non-transitorily” will be understood to refer to a non-ephemeral state for the stored contents (and hence excludes when the stored contents merely constitute signals or waves) rather than volatility of the storage media itself and hence includes both non-volatile memory (such as read-only memory (ROM) as well as volatile memory (such as an erasable programmable read-only memory (EPROM).

The control circuit 202 is configured to cause transmission of the condition data and determine to which device to transmit the condition data. In some embodiments, while the child device 210 would prefer to transmit the condition data to the parent device 212, such transmission may not be possible. When transmitting the condition data, the control circuit 202 causes transmission of a discovery message. The discovery message is a one-to-many message seeking other devices to which the condition data can be transmitted.

The control circuit 202 receives acknowledgment messages from the other devices based on the discovery message. The acknowledgment messages include information about the sender of the acknowledgment message. For example, an acknowledgment message may contain an identifier of the device sending the message (e.g., a serial number or ID number), a location of the device sending the message, a type of the device sending the message (e.g. child device, parent device, master device, backend server, etc.), timestamp information, memory capacity information, etc. The control circuit 202 determines to which device to transmit the condition data based on the discovery messages. For example, the control circuit 202 may transmit the condition data to the parent device 212 if the control circuit 202 has received an acknowledgement message from the parent device 212 regardless of what other devices have responded. However, if multiple parent devices have responded to the control circuit’s 202 discovery message, the control circuit 202 may choose from the responding parent devices based on capacity, location, etc.

If the parent device 212 (or any other parent device, if any) is not reached, the control circuit 202 determines from the other devices responding to the acknowledgment message to whom to transmit the condition data. This determination can be based on any suitable information, as discussed previously. As one example, if the acknowledgment message does not reach the parent device 212, the child device 210 can transmit the condition data to a child device having the greatest memory capacity or greatest available memory. As another example, the child device 210 can transmit the condition data to whichever non-parent device (e.g., another child device or an intermediate device) that is furthest from the child device 210. In such embodiments, the control circuit 202 can determine to which other device to transmit the condition data based on the Bellman-Ford algorithm. In any case, the ultimate goal is for the child device’s 210 condition data to eventually reach the parent device 212 (or any other parent device). In this manner, the child device 210, as well as any other child devices and/or other devices can act as a mesh network.

The parent device 212 stores the condition data received from the child device 210 and/or any other devices. Accordingly, the parent device 212 can include a parent device memory 214. The parent device memory 214 can be of any suitable type. In some embodiments, the parent device memory 214 is larger than the child device memory 208 to accommodate storage of condition data from a number of child devices. The parent device 212 stores the condition data received from the child devices until the parent device 212 can transmit the condition data to a master device. Once the parent device reaches a master device, the parent device 212 transmit the condition data received from the child devices to the master device, via, for example, a parent device transmitter 216. In some embodiments, the parent device transmitter 216 acts as a transceiver, receiving condition data (and any other relevant messages and/or data) from child devices and transmitting condition data (and any other relevant messages and/or data) to master devices and/or child devices.

While the discussion of FIG. 2 provides detail regarding a system for monitoring condition compliance, the discussion of FIG. 3 describes example operations for monitoring condition compliance.

FIG. 3 is a flow chart depicting example operations for monitoring condition compliance, according to some embodiments. The flow begins at block 302.

At block 302, condition data is captured. For example, the condition data can be captured by one or more sensors associated with a child device (i.e., a child device sensor). The child device is configured to be incorporated with a container housing a product. For example, the child device can be placed in, attached, to, placed near, etc. the container. The child device sensor can capture any type of condition data desired. Accordingly, the child device sensor can be any suitable type of sensor. The flow continues at block 304.

At block 304, the condition data is stored. For example, the child device can store the condition data. The child device can store the condition data in a child device memory. The flow continues at block 306.

At block 306, a discovery message is transmitted. For example, the child device can transmit the discover message. The child device can transmit the discovery message via a transmitter (e.g., a child device transmitter). The discovery message is a one-to-many message seeking information from other devices. The discovery message can solicit information from the other devices and can include information about the child device (e.g., an identification, location, etc. of the child device). The flow continues at block 308.

At block 308, acknowledgment messages are received. For example, the child device can receive the acknowledgment messages. The child device can receive the acknowledgment messages via the child device transmitter, acting as a transceiver, or a child device receiver. The acknowledgment messages can include information about the device sending the acknowledgment messages (e.g., an identifier of the device sending the message (e.g., a serial number or ID number), a location of the device sending the message, a type of the device sending the message (e.g. child device, parent device, master device, backend server, etc.), timestamp information, memory capacity information, etc.). The flow continues at decision diamond 310.

At decision diamond 310, it is determined if a parent device was reached. For example, the child device can determine, based on the acknowledgment messages, if a parent device was reached. The child device can make this determination via a control circuit. In some embodiments, a parent device is reached if a parent device responds to the child devices discovery message and/or has capacity to accept additional condition data. If a parent device is reached, the flow continues at block 312. If a parent device is not reached, the flow continues at block 314.

At block 312, a parent device was reached and condition data is transmitted. For example, the child device can transmit the condition data to the parent device. The control circuit can cause transmission of the condition data. In some embodiments, the condition data includes additional information. For example, the condition data can include an identifier of the child device, a location of the child device, timestamp information, etc. After the child device has transmitted the condition data, the flow continues at block 318. However, as previously discussed, if a parent device was not reached, the flow continues from decision diamond 310 to block 314.

At block 314, a parent device was not reached and another child device is determined. For example, the child device, via the control circuit, can determine another child device to which to transmit the condition data. The control circuit determines the other child device from the devices that transmitted acknowledgment messages. In some embodiments, the goal is for the condition data to eventually reach a parent device. In such embodiments, the control circuit selects a child device from the child devices that responded to the discovery message based on this goal. In one embodiment, the control circuit selects the child device as the furthest device from the child device that responded to the discover message. The flow continues at block 316.

At block 316, the condition data is transmitted. For example, the child device can transmit the condition data. The control circuit can cause the transmission of the condition data. The condition data is transmitted to the determined child device. In some embodiments, the condition data includes additional information. For example, the condition data can include an identifier of the child device, a location of the child device, timestamp information, etc. In some embodiments, the determined child device attempts to transmit the received condition data to a subsequent child device and/or a parent device until the condition data is transmitted to a parent device. The flow continues at block 318.

At block 318, condition data is stored. For example, the parent device stores the condition data. The condition data is condition data received from a number of child devices. The parent device stores the condition data until it reaches a master device. The flow continues at block 320.

At block 320, condition data is transmitted. For example, the parent device can transmit the condition data to a master device. The condition data is condition data received from a number of child devices.

In some embodiments, a system for monitoring condition compliance comprises a child device, wherein the child device is configured to be incorporated with a container housing a product, the child device comprising a child device sensor, wherein the child device sensor is configured to capture condition data associated with the product, a child device memory, wherein the child device memory is configured to store the condition data associated with the product, a child device transmitter, wherein the child device transmitter is configured to transmit the condition data associated with the product, and a control circuit, wherein the control circuit is configured to cause transmission, via the child device transmitter, of a discovery message, receive, from other devices via the child device transmitter, acknowledgment messages, determine, based on the acknowledgment messages, if the discovery message reached a parent device, if the discovery message reached a parent device, cause transmission of the condition data associated with the product to the parent device, and if the discovery message did not reach a parent device, determine, from the other devices, one of the other devices that is furthest from the child device, and cause transmission of the condition data associated with the product to the one of the other devices furthest from the child device, and the parent device, the parent device configured to store condition data received from a plurality of child devices, and transmit, to a master device, the condition data received from the plurality of child devices.

In some embodiments, an apparatus and a corresponding method performed by the apparatus comprises capturing, by a child device sensor associated with a child device, condition data associated with a product, wherein the child device is incorporated with a container housing the product, storing, by a child device memory, the condition data associated with the product, transmitting, via a child device transmitter, the condition data associated with the product, receiving, via the child device transmitter from other devices, acknowledgment messages, determining, by a control circuit of the child device based on the acknowledgment messages, whether the discovery message reached a parent device, if the discovery message reached a parent device, transmitting, via the child device transmitter, the condition data associated with the product to the parent device, if the discovery message did not reach a parent device, determining, from the other devices, one of the other devices that is furthest from the child device, and transmitting, via the child device transmitter, the condition data associated with the product to the one of the other devices that is furthest from the child device, storing, by the parent device, condition data associated with a plurality of child devices, and transmitting, by the parent device to a master device, the condition data received from the plurality of child devices.

Those skilled in the art will recognize that a wide variety of other modifications, alterations, and combinations can also be made with respect to the above described embodiments without departing from the scope of the invention, and that such modifications, alterations, and combinations are to be viewed as being within the ambit of the inventive concept. 

1. A system for monitoring condition compliance of products, the system comprising: a child device, wherein the child device is configured to be incorporated with a container housing a product, child device comprising: a child device sensor, wherein the child device sensor is configured to capture condition data associated with the product; a child device memory, wherein the child device memory is configured to store the condition data associated with the product; a child device transmitter, wherein the child device transmitter is configured to transmit the condition data associated with the product; and a control circuit, wherein the control circuit is configured to: cause transmission, via the child device transmitter, of a discovery message; receive, from other child devices via the child device transmitter, acknowledgment messages; determine, from the other child devices, one of the other child devices that is further from the child device than another of the child devices; and cause transmission of the condition data associated with the product to the one of the other child devices further from the child device than another of the child devices.
 2. (canceled)
 3. The system of claim 1, wherein the child device transmitter is configured to transmit via a radio wave frequency.
 4. (canceled)
 5. The system of claim 1, wherein the child device further comprises: a weight sensor, wherein the weight sensor is configured to detect the product in the container.
 6. The system of claim 5, wherein the control circuit is further configured to: receive, from the weight sensor, an indication that the product is in the container; and cause, based on the indication that the product is in the container, the child device to turn on.
 7. The system of claim 1, wherein the condition data associated with the product is one or more of a temperature, a humidity, light exposure, orientation, and a presence of moisture.
 8. The system of claim 1, wherein the container is located in a cargo area, and wherein the child device sensor captures the data associated with the product during transport.
 9. The system of claim 1, wherein the control circuit determines the one of the other child devices that is further from the child device than another of the child devices based on a Bellman-Ford algorithm.
 10. A method for monitoring condition compliance of products, the method comprising: capturing, by a child device sensor associated with a child device, condition data associated with a product, wherein the child device is incorporated with a container housing the product; storing, by child device memory, the condition data associated with the product; transmitting, via a child device transmitter, a discovery message; receiving, via the child device transmitter from other child devices, acknowledgment messages; determining, from the other devices, one of the other child devices that is further from the child device than another of the child devices; and transmitting, via the child device transmitter, the condition data associated with the product to the one of the other child devices that is further from the child device than another of the child devices.
 11. (canceled)
 12. The method of claim 10, wherein the child device transmitter is configured to transmit via a radio wave frequency.
 13. (canceled)
 14. The method of claim 10, wherein the child device includes a weight sensor configured to detect the product in the container.
 15. The method of claim 14, further comprising: receiving, from the weight sensor, an indication that the product is in the container; and causing, based on the indication that the product is in the container, the child device to turn on.
 16. The method of claim 10, wherein the condition data associated with the product is one or more of a temperature, a humidity, light exposure, orientation, and a presence of moisture.
 17. The method of claim 10, wherein the container is located in a cargo area, and wherein the child device sensor captures the data associated with the product during transport.
 18. The method of claim 10, wherein the determining the one of the other child devices that is further from the child device than another of the child devices is based on a Bellman-Ford algorithm. 